Repository navigation
Run WebGPU tests on self-hosted CI - #9406
Open
davepagurek wants to merge 14 commits into
Open
davepagurek wants to merge 14 commits into
davepagurek wants to merge 14 commits into
Conversation
This reverts commit eb9d8cf.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
So currently we don't run the WebGPU tests on CI when contributors make changes. This currently means I have to manually clone people's changes and run them myself to confirm, so WebGPU changes are especially painful to review.
The problem is that while Chrome's SwiftShader-based CPU fallback works on CI for WebGL, there isn't an equivalent for WebGPU, and GitHub's free Actions runners do not have a real GPU attached.
A possible workaround that's "free" (ish) is to use self-hosted runners. I've got a server in my closet that I can run this on. The idea is that:
I've tested this over on my fork of p5 here davepagurek#2 and using this project to manage the orchestrator/job runner: https://github.com/davepagurek/p5-ci-runner/
The required changes in the p5 repo were:
Before merging this I need to get a personal access token for the real p5 repo, not my fork, and attach my server, and then we should see tests run here.